📄 CodeRabbit inference engine (CLAUDE.md)

Always prefer console commands over log commands. Use console.log instead of log.info

Files:

• server/src/services/ito/transcribeStreamV2Handler.ts
• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (.cursor/rules/always.mdc)

Never use empty catch statements

Files:

• server/src/services/ito/transcribeStreamV2Handler.ts
• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (.cursor/rules/code-conventions.mdc)

**/*.{ts,tsx}: Follow standard, idiomatic TypeScript coding practices for structure, naming, and types
Avoid adding comments unless they explain complex logic or non-obvious decisions; well-written, self-explanatory code is preferred
Do not add comments that merely restate what the code does
Rely on comprehensive tests to document the behavior and usage of code rather than extensive comments within the code itself
Use kebab-case when naming directories, TypeScript, and other files

**/*.{ts,tsx}: Prefer interfaces over types for object definitions
Use type for unions, intersections, and mapped types
NEVER use any or as any types or coercion
Leverage TypeScript's built-in utility types
Use generics for reusable type patterns
Use PascalCase for type names and interfaces
Use camelCase for variables and functions
Use UPPER_CASE for constants
Use descriptive names with auxiliary verbs (e.g., isLoading, hasError)
Prefix interfaces for React props with 'Props' (e.g., ButtonProps)
Keep type definitions close to where they're used
Export types and interfaces from dedicated type files when shared
Co-locate component props with their components
Use explicit return types for public functions
Use arrow functions for callbacks and methods
Implement proper error handling with custom error types
Use function overloads for complex type scenarios
Prefer async/await over Promises
Prefer function declarations over function expressions
Use readonly for immutable properties
Leverage discriminated unions for type safety
Use type guards for runtime type checking
Implement proper null checking
Avoid type assertions unless necessary
Handle Promise rejections properly

Files:

• server/src/services/ito/transcribeStreamV2Handler.ts
• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (AGENTS.md)

Backend code and database migrations should be organized in server/ using Bun

Files:

• server/src/services/ito/transcribeStreamV2Handler.ts

📄 CodeRabbit inference engine (AGENTS.md)

{app,lib,server}/**/*.{ts,tsx,js,jsx}: Use ESLint to enforce code style and run bun run lint before submitting code
Always use console commands instead of log commands (e.g., console.log instead of log.info)

Files:

• server/src/services/ito/transcribeStreamV2Handler.ts
• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (AGENTS.md)

Constants use SCREAMING_SNAKE_CASE naming convention

Files:

• server/src/services/ito/transcribeStreamV2Handler.ts
• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (.cursor/rules/react.mdc)

**/*.tsx: Use kebab-case for files and directories
Do not use 'use client' or 'use server' statements in React components
Favor named exports for components
Ensure components are modular, reusable, and maintain a clear separation of concerns
Always split React components so there is only ever one per file
Keep logic as low as possible in React components
Implement responsive design with Tailwind CSS using a mobile-first approach

Files:

• app/components/home/SubscriptionStatusWidget.tsx
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (AGENTS.md)

Electron renderer code should be organized in the app/ directory and use React + Tailwind

Files:

• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (AGENTS.md)

Use Prettier with 2-space indent for code formatting across TypeScript and React files

Files:

• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (AGENTS.md)

{app,lib}/**/*.{ts,tsx}: Components and classes use PascalCase naming convention
Hooks and utility functions use camelCase naming convention

Files:

• app/components/home/SubscriptionStatusWidget.tsx
• app/utils/userMetrics.ts
• app/components/home/contents/HomeContent.tsx

📄 CodeRabbit inference engine (AGENTS.md)

Co-locate Tailwind styles with React components and reuse tokens via lib/constants

Files:

• app/components/home/SubscriptionStatusWidget.tsx
• app/components/home/contents/HomeContent.tsx

Learnt from: julgmz
Repo: heyito/ito PR: 446
File: app/components/home/HomeKit.tsx:236-236
Timestamp: 2025-11-24T21:51:44.018Z
Learning: In app/components/home/SubscriptionStatusWidget.tsx, the hardcoded default wordsUsed value (1000) is intentional as a temporary placeholder until a future feature implements real usage tracking.

Applied to files:

• app/components/home/SubscriptionStatusWidget.tsx

app/hooks/useBillingState.ts (1)

• useBillingState (44-191)

app/store/useMainStore.ts (1)

• useMainStore (49-68)

app/utils/userMetrics.ts (1)

• calculateWeeklyWordCount (36-47)

app/utils/userMetrics.ts (1)

• calculateAllStats (135-148)